Require Description Resources to be supported #371
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| @@ -753,7 +753,8 @@ <h4 property="schema:name">Web Access Control</h4> | |||
| <section id="auxiliary-resources-description-resource" inlist="" rel="schema:hasPart" resource="#auxiliary-resources-description-resource"> | |||
| <h4 property="schema:name">Description Resource</h4> | |||
| <div datatype="rdf:HTML" property="schema:description"> | |||
| <p>An auxiliary resource of type <em>Description Resource</em> provides a description of a subject resource ([<cite><a class="bibref" href="#bib-ldp">LDP</a></cite>]).</p> | |||
| <p>An auxiliary resource of type <em>Description Resource</em> provides a description of a subject resource ([<cite><a class="bibref" href="#bib-ldp">LDP</a></cite>]). | |||
| <span about="" id="server-description-required" rel="spec:requirement" resource="#server-description-required"><span property="spec:statement"><span rel="spec:requirementSubject" resource="spec:Server">Servers</span> <span rel="spec:requirementLevel" resource="spec:MUST">MUST</span> support this auxiliary resource type.</span></span></p> | |||
There was a problem hiding this comment.
And how is it identified? What does supporting it mean?
There was a problem hiding this comment.
So, this is language pointing at the more generic language in the spec, which also needs work. The rel value is defined in a table, the protocol specific things are there too, the lifecycle assumptions also. I recognize it is in many contexts, including this, a bit problematic to just say "support", but I also tend to think that the tests is a venue to provide authoritative interpretations.
This is mostly to fix the immediate omission that describedby wasn't required in 0.9.
|
Updated re #372 . Let's move on. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, there is no server requirement to support
describedbyresources, only a description about how clients may discover them. I believe this to be a simple omission, it has been in Solid since the dawn of ages, and even though we want to generalize aux resources, this basic functionality should be required in 0.9.x.There are also tests solid-contrib/specification-tests#65 in this area, and I believe it is appropriate to make this a requirement rather than introduce more variability.